feat(robinhood): chain registry + RPC + launch tool support - #53
Merged
Merged
Conversation
- clawmes/lib/chains.py: 4663 (robinhood) + 46630 (robinhood-testnet)
Chain entries. get_chain("robinhood") now resolves.
- clawmes/services/rpc.py: default endpoints for Robinhood (4663) and
Robinhood Testnet (46630); CLAWMES_RPC_4663 / CLAWMES_RPC_46630 env
overrides work unchanged.
- clawmes/tools/clawnch_launch.py: schema accepts `chain`; forwarded as
`chain` query param via `prepare_deploy` when the caller selects the
Robinhood path (Bags.fm) instead of the Base/Clanker custodial path.
Chain is read off the API response (`data.chainId`) so emitted UI
artifacts link to Blockscout rather than Basescan on Robinhood launches.
- clawmes/services/clawnch.py: `prepare_deploy` takes + forwards `chain`
as a query param; docstring documents the Robinhood branch semantics
(no burn gate, Bags claimer array carries the 80/20 fee split instead
of Clanker's rewards array).
- clawmes/tools/clawnch_fees.py: docstring notes BagsFeeShare.claim() is
the Robinhood claim surface (per-token), separate from Clanker's
FeeLocker on Base.
- allowlist: unblock the plugin's own RHC hosts (rpc mainnet/testnet, blockscout x2, bags.fm) + startup self-check so a blocked shipped default is logged at start, not at first use - clawnch service: RHC launch-router flows — rh_ticket / rh_confirm_launch / rh_deposit_launch, rh_claimable / rh_claim, rh_launches, RHC $CLAWNCH info and link helpers; tickets validated as chainId 4663; Base-only surfaces (deploy, prepare_deploy) raise unsupported_chain instead of silently hitting the wrong chain - tools: clawnch_launch rh_ticket/rh_confirm/rh_deposit/rh_token and clawnch_fees rh_launches/rh_claimable/rh_claim; RHC-aware receipt cards - tests: +112 (5028 pass, 8 skipped, 100% coverage; mypy back at the pristine 113-error baseline)
- version 0.20.0 -> 0.21.0 (pyproject + _version.py); first PyPI release since 0.18.2 (includes unpublished 0.19.0/0.20.0 changes) - CHANGELOG: 0.21.0 section for the RHC launch surface, allowlist fix and no-silent-fallback changes; documents the new mcp>=1.0,<2 pin (the MCP 2.x SDK renamed the tool API the server targets)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds Robinhood Chain (4663) to the three surfaces the plugin exposes: chain registry, RPC service, and the Clawnch launch tool. This is the Hermes-side companion to clawnchdev/clawnch#15 and clawnchdev/clawncher#3.
Changes
clawmes/lib/chains.py— 4663 + 46630Chainentries.get_chain("robinhood")resolves.clawmes/services/rpc.py— default endpoints for Robinhood mainnet and testnet.CLAWMES_RPC_4663/CLAWMES_RPC_46630overrides work unchanged.clawmes/tools/clawnch_launch.py— schema acceptschain; forwarded toClawnchService.prepare_deploy(..., chain=...), which routes into clawnch'sLAUNCH_CHAIN-awareprepare/deployendpoint. Chain is read off the API response (data.chainId) so emitted UI artifacts point at Blockscout on Robinhood.clawmes/services/clawnch.py—prepare_deploytakes + forwards thechainquery param. Docstring documents the Robinhood branch (Bags claimer array carries the 80/20 fee split; no burn gate).clawmes/tools/clawnch_fees.py— docstring notes the Robinhood claim surface is per-tokenBagsFeeShare.claim().Default behavior
Base remains the default.
prepare_deployonly invokes the Robinhood branch when the caller supplieschain=robinhood; everything else flows through the existing Clanker custodial path.Follow-ups
/burnand/launch burnflows don't apply on Robinhood; separate design note./claimroster for Robinhood launches (BagsFeeShare readers per token).Cross-links